A graph that purports to show GeekBench 3 scores for Apple's anticipated A9-series application processors paints a picture of significant performance improvements, beating out even Samsung's latest 8-core chips.
Apple's A9 chimes in with a single-core score of 2090 and a multi-core tally of 3569, compared to the respective averages of 1611 and 2892 shown by the A8 found in the iPhone 6 series. The A9X chalks up 2109 and 5101 in the same benchmarks, compared to 1808 and 4526 for the iPad Air 2's A8X.
Samsung's Exynos 7420 — Â which powers the flagship S6, S6 Edge, Note 5, and S6 Edge+ — Â bests Apple's A9 on multi-core workloads with a score of 5048, but falls behind on single-core tasks by posting a 1486. Huawei's Kirin 950 and LG's Nuclun 2 also beat out Samsung's entry.
The graph — Â the authenticity of which cannot be determined — comes from Weibo via GforGames.
Apple is expected to reveal the A9 alongside a set of new iPhones at a special event early next month. The A9X — Â which is likely to debut alongside a new iPad — Â might bow at the same event, though it's not clear whether Apple plans to hold a separate iPad introduction at a later date.
Samsung and TSMC are believed to have begun mass production for the A9 in July.
61 Comments
Anytime you compare processor performance for a mobile device, you need to also compare battery usage.
Anytime you compare processor performance for a mobile device, you need to also compare battery usage.
The same as all the other tests for the past few years.
Samsung's battery life will suck, as usual.
Apple's battery life will - as usual - be the gold standard.
I'm curious how the Fandroid community will defend this pathetic performance. Apple's A9x with less cores runs faster than that 8-core garbage. Shameful.
That doesn't sound much. But even when this is true, Geekbench doesn't measure GPU performance, which is the most important factor.
Uh, the Exynos 7420 gets 4099 on the S6 and 4386 on S6 Edge. Don't know where you got that 5048 number from, but it's not from Geekbench. Probably another "loaded" result, as is so common on Android devices.
Is this the fake benchmark I've read about today? https://mobile.twitter.com/jfpoole/status/632066813380165632